翻訳と辞書
Words near each other
・ Requena Province
・ Requena, Loreto
・ Requena, Valencia
・ Requena-Utiel
・ Requerimiento
・ Requesens
・ Requesens Castle
・ Request
・ Request (broadcasting)
・ Request (Juju album)
・ Request (The Awakening album)
・ Request + Line
・ ReQuest Dance Crew
・ Request for admissions
・ Request for any other privilege
Request for Comments
・ Request for evidence
・ Request for information
・ Request for information (parliamentary procedure)
・ Request for permission to withdraw or modify a motion
・ Request for production
・ Request for proposal
・ Request for quotation
・ Request for Routing
・ Request for tender
・ Request for waiver
・ Request line
・ Request price quotation
・ Request stop
・ Request to be excused from a duty


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Request for Comments : ウィキペディア英語版
Request for Comments

A Request for Comments (RFC) is a type of publication from the Internet Engineering Task Force (IETF) and the Internet Society, the principal technical development and standards-setting bodies for the Internet.
An RFC is authored by engineers and computer scientists in the form of a memorandum describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. It is submitted either for peer review or simply to convey new concepts, information, or (occasionally) engineering humor. The IETF adopts some of the proposals published as RFCs as Internet Standards.
Request for Comments documents were invented by Steve Crocker in 1969 to help record unofficial notes on the development of ARPANET. RFCs have since become official documents of Internet specifications, communications protocols, procedures, and events.〔(【引用サイトリンク】title=RFC's, Internet Request For Comments )
==History==
The inception of the RFC format occurred in 1969 as part of the seminal ARPANET project. Today, it is the official publication channel for the Internet Engineering Task Force (IETF), the Internet Architecture Board (IAB), and — to some extent — the global community of computer network researchers in general.
The authors of the first RFCs typewrote their work and circulated hard copies among the ARPA researchers. Unlike the modern RFCs, many of the early RFCs were actual requests for comments and were titled as such to avoid sounding too declarative and to encourage discussion.〔Hafner, Katie; Lyon, Matthew (1996). Where Wizards Stay Up Late: The Origins of the Internet.〕 The RFC leaves questions open and is written in a less formal style. This less formal style is now typical of Internet Draft documents, the precursor step before being approved as an RFC.
In December 1969, researchers began distributing new RFCs via the newly operational ARPANET. RFC 1, entitled "Host Software", was written by Steve Crocker of the University of California, Los Angeles (UCLA), and published on April 7, 1969. Although written by Steve Crocker, the RFC emerged from an early working group discussion between Steve Crocker, Steve Carr and Jeff Rulifson.
In RFC 3, which first defined the RFC series, Crocker started attributing the RFC series to the Network Working Group. Rather than being a formal committee, it was a loose association of researchers interested in the ARPANET project. In effect, it included anyone who wanted to join the meetings and discussions about the project.
Many of the subsequent RFCs of the 1970s also came from UCLA, because UCLA was one of the first Interface Message Processors (IMPs) on ARPANET.
The Augmentation Research Center (ARC) at Stanford Research Institute, directed by Douglas Engelbart, was another of the four first ARPANET nodes and the source of early RFCs.
The ARC became the first network information center (InterNIC), which was managed by Elizabeth J. Feinler to distribute the RFCs along with other network information. From 1969 until 1998, Jon Postel served as the RFC editor. On his death in 1998, his obituary was published as RFC 2468.
Following the expiration of the original ARPANET contract with the U.S. federal government, the Internet Society, acting on behalf of the IETF, contracted with the Networking Division of the University of Southern California (USC) Information Sciences Institute (ISI) to assume the editorship and publishing responsibilities under the direction of the IAB.
Sandy Ginoza joined USC/ISI in 1999 to work on RFC editing, and Alice Hagens in 2005.
Bob Braden took over the role of RFC project lead, while Joyce K. Reynolds continued to be part of the team until October 13, 2006.
In July 2007, ''streams'' of RFCs were defined, so that the editing duties could be divided. IETF documents came from IETF working groups or submissions sponsored by an IETF area director from the Internet Engineering Steering Group. The IAB can publish its own documents. A research stream of documents comes from the Internet Research Task Force (IRTF), and an independent stream from other outside sources.〔(【引用サイトリンク】author= Leslie Diagle )
A new model was proposed in 2008, refined, and published in August 2009, splitting the task into several roles,〔(【引用サイトリンク】author= O. Kolkman, Ed )
including the RFC Series Advisory Group (RSAG).
(The model was updated in 2012
)
The streams were also refined in December 2009, with standards defined for their style.〔(【引用サイトリンク】author= Leslie Diagle, Olaf Kolkman )
In January 2010 the RFC editor function was moved to a contractor, Association Management Solutions, with Glenn Kowack serving as interim series editor.
In late 2011, Heather Flanagan was hired as the permanent RFC Series Editor.
Also at that time, an RFC Series Oversight Committee (RSOC) was created.〔(【引用サイトリンク】author= RFC Editor )

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Request for Comments」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.